Data storage device

ABSTRACT

A data storage device including a non-volatile semiconductor memory and an attribute information storage unit. In an attribute information storage unit of the data storage device, there are stored the number of sectors in one block and the information indicating the logical address of a sector lying at a block boundary. A host device, on which is mounted the data storage device, grasps the number of clusters that make up one block in the data storage device and the location of the leading cluster position of the block and records the data on the block basis.

TECHNICAL FIELD

This invention relates to a data storage device having an inner non-volatile semiconductor memory. This application claims priority of Japanese Patent Application No.2002-112641, filed in Japan on Apr. 15, 2002, the entirety of which is incorporated by reference herein.

BACKGROUND ART

Up to now, as an electrically erasable non-volatile memory, a NAND flash memory has been in use. With this sort of the NAND flash memory, new data is written as data recorded therein has been erased. The flash memory is provided with an erasure block for batch-wise data erasure and, after the recorded data has been erased on the erasure block basis, new data is written in the memory. With the flash memory, the size of the erasure block differs from that of the data write unit (physical sector) such that plural physical sectors are provided in one erasure block.

In the flash memory, data needs to be recorded towards a physically fixed direction in one erasure block. The reason in that, in case data has been recorded in an optional physical sector in the erasure block, the contents of the recorded data are kept as for the sectors lying in a fixed direction from the sector of interest, while the contents of the recorded data are not necessarily kept as for the sectors lying in the opposite direction from the sector of interest. Thus, with the flash memory, the routine practice is to set the physical addresses and the logical addresses in such a manner that, if the data are recorded in a forward direction, the contents of the recorded data are necessarily assured. Meanwhile, the contents of data recorded in an erasure block different from the erasure block as a subject of recording are assured at all times without dependency on the data recording position.

As a form of application of this NAND flash memory, there is known a removable small-sized IC memory, termed a memory card. The memory card is able to store a large variety of digital data, such as still image data, moving picture data, speech data or music data. For this reason, the memory card is used as an external storage medium in a wide variety of host devices, such as a portable information terminal, a desk top computer, a notebook computer, a mobile phone, an audio device or a household electrical device.

The host device, employing the memory card as an external storage medium, is sometimes provided with an internal storage medium, such as a hard disc. The hard disc is usually accessed with a logical format from the host device, using a file system, called the MS-DOS (trademark), as a vehicle. For compatibility to such other storage mediums, the common file system, including the MS-DOS, is desirably applicable to the memory card.

The MS-DOS provides for a unit, termed a cluster, as an accessing unit for a storage medium. The MS-DOS generates the FAT (file allocation table), in terms of this cluster, as a unit, to oversee the relationship of interconnections of data recorded in the storage medium. Thus, the host device logically accesses the storage medium, on the cluster basis, to read out data recorded on the storage medium, or to write data on the storage medium.

Meanwhile, in the conventional memory card, the flash memory has a smaller capacity, with the cluster size coinciding with the erasure block size. Thus, as long as data is recorded on the cluster basis, the contents of the recorded data are kept, without dependency on the sort of the recording performed.

However, as the capacity of the flash memory is increased and, in keeping up therewith, the erasure block is increased in size, the cluster size of a memory card employing a flash memory of an increased capacity becomes smaller than the erasure size, if the MS-DOS is used in the file system. When the cluster size is smaller than the erasure block size, and data recording is made on the cluster basis, there is a possibility that the contents of the recorded data may not necessarily be kept.

For keeping the contents of the recorded data, in the memory card employing the flash memory of an increased capacity, the processing for producing a memory area, termed a garbage collection, is carried out, in case the represented cluster is located in rear of the cluster as the subject of writing.

Specifically, the garbage collection in the memory card is carried out as follows:

When data is to be written in a certain cluster in an erasure block, it is verified whether or not there is any recorded valid data in a cluster the address for which is on the rear side of the address of the cluster as a subject of writing in the erasure block. In case the recorded valid data is located in a cluster the address for which is on the rear side with respect to the address of the cluster as the subject of writing in the erasure block, all data in the erasure block, with the exception of the data of the cluster of interest, are temporarily read out to a buffer. A new erasure block is produced and data corresponding to the synthesis of the data in the buffer and the data as the subject of writing is written in the so produced new erasure block.

This processing is the processing of garbage collection performed in the memory card. The garbage collection is routinely executed in the CPU in the memory card and hence is not recognized by the operating system of the host device.

In this manner, redundant operations, such as data readout and buffering, need to be performed in the garbage collection in the memory card, despite the fact that the processing is carried out at the time of recording. As a consequence, the speed of recording between the host device and the memory card is lowered on the occasion of the occurrence of the garbage collection. It is therefore inherently desirable that data recording may be made at all times without producing garbage collection.

For not producing the garbage collection, it is sufficient if the physical address in the memory is directly supervised from the host side in the course of data writing. However, with the MS-DOS, the medium is not managed by the physical address, so that, for directly accessing the physical addresses in the memory, it is necessary to apply a special file system different from the MS-DOS. This, however, is not desirable because compatibility with other mediums may not be maintained with such special file system.

DISCLOSURE OF THE INVENTION

It is therefore an object of the present invention to provide a novel data storage device whereby the problem inherent in the conventional data storage medium, such as IC memory device, may be overcome.

It is another object of the present invention to provide a data storage device in which, even in case a file system with the maximum size of the data accessing unit for a semiconductor memory smaller than the eras block size of the semiconductor memory is used, data can be recorded without producing so-called garbage collection.

For accomplishing these objects, the present invention provides a removable data storage device detachably mounted to a host apparatus, comprising a non-volatile semiconductor memory in which data recorded thereon is erased batch-wise in terms of a block of a predetermined data volume as a unit, and a system information storage unit having the inner information of the data storage device recorded therein. A user area, as an area in which data is recorded by a user, is provided in a storage area of the semiconductor memory, and file management data corresponding to the logical format supervising the recorded data by setting logical addresses from one sector as a data read/write unit to another and also supervising the relationship of interconnection of the recorded data in terms of a cluster, composed of a predetermined number of physically consecutive sectors, as a unit, is recorded in the user are. This user area is accessed by the host apparatus based on the logical format. The number of sectors in one block and the information indicating the logical address of the sector of the block boundary position are stored in the system information storage unit.

Other objects, features and advantages of the present invention will become more apparent from reading the embodiments of the present invention as shown in the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view showing a memory card embodying the present invention and a host device employing this memory card.

FIG. 2 is a perspective view showing the memory card from its front side.

FIG. 3 is a perspective view showing the memory card from its rear side.

FIG. 4 is a block diagram showing an internal block structure of the memory card.

FIG. 5 shows the structure of the interfacing functions for data transfer between the memory card and the host device.

FIG. 6 shows a data structure recorded in an attribute information area.

FIG. 7 is a flowchart showing data recording processing contents of the host device.

FIG. 8 depicts an image of a medium in case the format of a first specified instance is applied.

FIG. 9 depicts the values of the parameters in case the format of the first specified instance is applied.

FIG. 10 depicts the contents of description of MBR in case the format of the first specified instance is applied.

FIG. 11 depicts the contents of description of PBR in case the format of the first specified instance is applied.

FIG. 12 depicts an image of a medium in case the format of a second specified instance is applied.

FIG. 13 depicts values of respective parameters in case the format of the second specified instance is applied.

FIG. 14 depicts the contents of description of MBR in case the format of the second specified instance is applied.

FIG. 15 depicts the contents of description of MBR in case the format of the second specified instance is applied.

FIG. 16 depicts the state of the FAT in case the format of the first specified instance is applied.

FIG. 17 depicts the state of the FAT in case the format of the second specified instance is applied.

FIG. 18 depicts an image of a medium of a routine format.

FIG. 19 depicts an image of a medium of a memory card in which the cluster size is smaller than the block size.

FIG. 20 depicts an image of a medium of a memory card in which the block size is equal to the cluster size.

BEST MODE FOR CARRYING OUT THE INVENTION

In the following, such an instance in which the present invention is applied to a removable small-sized IC memory device, and such an instance in which the present invention is applied to a data processing apparatus employing this small-sized IC memory device as an external storage medium, are explained.

In the following explanation, a small-sized IC memory device is termed a memory card, whilst a data processing apparatus, to which the memory card is connected, is termed a host device.

First, the schematics of the host device embodying the present invention and the memory card connected to this host device are explained by referring to FIG. 1.

A memory card 1 of the present invention includes an inner non-volatile semiconductor memory (IC memory), and is able to store various digital data, such as still picture data, moving picture data, speech data and music data. This memory card 1 operates as an external storage medium for a host device 2, such as, for example a portable information terminal, a desk top computer, a notebook computer, a mobile phone, audio equipment or a household electrical apparatus.

Referring to FIG. 1, the memory card 1 is used in such a state in which it is inserted into an insertion/removal port 3 provided to the host device 2. The memory card 1 can be freely inserted into and detached from the insertion/removal port 3 by a user. Thus, the memory card 1 inserted into a host device can be extracted therefrom and inserted into another host device. That is, the present memory card 1 can be used for exchanging data between the different host devices.

The memory card 1 and the host device 2 transfer data over a parallel interface employing a six line half duplex parallel protocol configured for transmitting six signals, namely 4-bit parallel data, a clock signal and a bus state signal.

Referring to FIG. 2, the memory card 1 of the present invention is formed as a substantially rectangular thin sheet, having a length L₁ along the longitudinal direction of 50 mm, a width W₁ of 21.45 mm and a thickness D₁ of 2.8 mm. The memory card 1 has its one surface as a front surface 1 a and its opposite surface as a reverse surface 1 b. On the reverse surface 1 b towards one longitudinal end of the memory card 1 are formed a set of connection terminals 4 as ten planar electrodes, as shown in FIG. 3. These electrodes, forming the set of the connection terminals 4, are provided parallel to one another along the width of the memory card 1. Between the neighboring electrodes, there are provided partitions S upstanding from the reverse surface 1 b. These partitions 5 serve for preventing the connection terminals, connected to the respective electrodes, from being contacted with the other electrodes. A slide switch 6 for prohibiting inadvertent erasure is provided centrally towards the aforementioned one end of the reverse surface 1 b of the memory card 1, as shown in FIG. 3.

The host device 2, to which is mounted the memory card 1, is provided with the insertion/removal port 3 for inserting and detaching the memory card 1. This insertion/removal port 3 is formed in the front surface of the host device 2 as an opening of the same width W₁ and thickness D₁ as those of the memory card 1, as shown in FIG. 1. The memory card 1, inserted into the host device 2 through the insertion/removal port 3, is held by the host device 2 against incidental detachment by the connection terminals of the host device 2 being connected to the respective electrodes that make up the set of the connection terminals 4. Meanwhile, the connection terminals, not shown, provided to the host device 2, are provided with ten contacts in meeting with the number of the electrodes that make up the set of the connection terminals 4 provided to the loaded memory card 1.

The memory card 1 according to the present invention is loaded on the host device 2, with its end provided with the set of the connection terminals 4 as an inserting end and with the direction of an arrow X₁ in FIG. 2 as an inserting direction. When the memory card 1 is loaded on the host device 2, the respective electrodes that make up the set of the connection terminals 4 are connected to the respective contacts of the connection terminals provided to the host device 2 to enable exchange of electrical signals.

The inner structure of the memory card 1 of the present invention is now explained with reference to FIG. 4.

The memory card 1 of the present invention includes a parallel interfacing (I/F) circuit 12, a register circuit 13, a data buffer circuit 14, an ECC circuit 15, a memory I/F controller 16, a non-volatile semiconductor memory 17, and an oscillation controlling circuit 18, as shown in FIG. 4.

The parallel I/F circuit 12 is a circuit for transmitting data with the host device 2 using the six-line half duplex parallel type data transfer protocol.

The register circuit 13 is a circuit for storage of operation controlling commands for the memory I/F controller 16, transferred from the host equipment, the inner states of the memory card 1, various parameters needed in executing the controlling commands, or the file management information in the non-volatile semiconductor memory 17. The operation controlling commands are referred to below as control commands. This register circuit 13 is accessed from both the host device 2 and the memory I/F controller 16. Meanwhile, the host device 2 accesses the register circuit 13, using a transfer protocol command TPC as provided for on the data transfer protocol of the present memory card That is, this TPC is used in case the host device 2 writes or reads out the control command or various parameters stored in the register circuit 13.

The data buffer circuit 14 is a memory circuit for transient storage of data written in the non-volatile semiconductor memory 17 and data read out from the non-volatile semiconductor memory 17. That is, when data is written from the host device 2 to the non-volatile semiconductor memory 17, data as a subject of writing is transferred from the host device 2 to the data buffer circuit 14 in accordance with the data transfer protocol and subsequently the data as a subject of writing, stored in the data buffer circuit 14, is written by the memory I/F controller 16 in the non-volatile semiconductor memory 17. When the data is read out from the non-volatile semiconductor memory 17 to the host device 2, the memory I/F controller 16 reads out data as a subject of readout from the non-volatile semiconductor memory 17 to store the read-out data transiently in the data buffer circuit 14. The data as a subject of readout is then transferred from the data buffer circuit 14 to the host device 2 in accordance with the data transfer protocol.

Meanwhile, the data buffer circuit 14 has a data capacity corresponding to a preset data write unit, such as, for example, the data capacity of 512 bytes, which is the same as the page size of the flash memory. Meanwhile, the host device 2 accesses the data buffer circuit 14 using the TPC. That is, if the host device 2 writes or reads out the data stored in the data buffer circuit 14, the TPC is used.

The ECC circuit 15 appends the error correction code (ECC) to data to be written in the non-volatile semiconductor memory 17. The ECC circuit 15 performs error correction coding on the read out data based on the error correction code appended to the data read out from the non-volatile semiconductor memory 17. For example, 3 bytes of the error correction code are appended to a data unit of 512 bytes.

The memory I/F controller 16 performs control, in accordance with control commands stored in the register circuit 13, for exchanging data between the data buffer circuit 14 and the non-volatile semiconductor memory 17, supervising data security of the non-volatile semiconductor memory 17, managing the other functions of the memory card 1, and for updating the data stored in the register circuit 13.

The non-volatile semiconductor memory 17 is e.g. a non-volatile semiconductor memory, such as a NAND type flash memory. The capacity of the non-volatile semiconductor memory 17 is e.g. 16 Mbytes, 32 Mbytes, 64 Mbytes or 128 Mbytes. The erasure block unit of the non-volatile semiconductor memory 17 is eg. 16 Kbytes. The read/write unit is also termed a page and is 512 bytes as is that of the data buffer circuit 14. The oscillation controlling circuit 18 generates operating clocks in the present memory card 1.

As the connection terminals of the memory card 1, there are provided VSS, VCC, DATA0, DATA1, DATA2, DATA3, BS, CLK and INS terminals. Since two terminals are provided as the VSS terminals, a total of ten connection terminals are provided in the memory card 1. Similar connection terminals are provided on the side of the host device 2.

To the VSS terminals is connected the VSS (reference 0 voltage). These VSS terminals connect the ground voltage of the host device to that of the memory card to establish a coincident zero volt reference potential of the host device and the memory card. The power supply voltage (VCC) is supplied to the VCC terminal from the host device.

The data signal (DATA0) of the lowermost bit of the 4-bit parallel data, transferred between the memory card 1 and the host device 2, is supplied to or output from the DATA0 terminal, The data signal (DATA1) of the second lower bit of the 4-bit parallel data, transferred between the memory card 1 and the host device 2, is supplied to or output from the DATA1 terminal. The data signal (DATA2) of the third lower bit of the 4-bit parallel data, transferred between the memory card 1 and the host device 2, is supplied to or output from the DATA2 terminal. The data signal (DATA3) of the fourth lower bit of the 4-bit parallel data, transferred between the memory card 1 and the host device 2, is supplied to or output from the DATA3 terminal.

A bus state signal is supplied from the host device to the memory card via BS terminal. A clock signal is supplied from the host device to the CLK terminal. The INS terminal is used for insertion/withdrawal detection for the host device 2 to check whether or not the memory card has been inserted into a slot formed in the host device 2. The INS terminal of the host device 2 is connected to a pull-up resistor, not shown.

Referring to FIG. 5, the functional structure of the interface for data transfer between the memory card 1 and the host device 2 is now explained.

In FIG. 5, the interfacing functions of the host device 2 are made up by a file manager 31, a TPC interface 32, and a parallel interface 33. The interfacing functions of the memory card 1 is made up by a parallel interface 33, a register 35, a data buffer 36, a memory controller 37 and a memory 38.

The file manager 31 is an operation system of the host device and supervises the files stored in the memory card 1 and the files stored in other mediums of the host device. In the present embodiment, the MS-DOS (Microsoft Disc Operating System, registered trademark) is used as an operating system in the file manager 31. The file manager 31 also supervises the other storage mediums connected to the host device 2 by the MS-DOS. The file manager 31 is a function implemented within a controller in the host device.

The TPC interface 32 is an interfacing function as a lower layer in the file manager 31. The TPC interface 32 accesses the register 35 and the data buffer 36 in the memory card 1 by the data transfer protocol which has defined the commands peculiar to the present interface (TPC: transfer protocol command). This TPC interface 32 is a function implemented by e.g. a controller in the host device 2.

The parallel interfaces 33, 34 represent lower layers in the TPC interface 32 and proves a physical hierarchical layer of the present interfacing system. The parallel interfaces 33, 34 transfer data in accordance with a six line half duplex parallel protocol configured for transmitting six signals, namely 4-bit parallel data, a clock signal and a bus state signal The parallel interfaces 33, 34 represent the functions implemented by the parallel I/F circuit 12.

The register 35 is designed to store control commands transmitted from the host, the inner state of the memory card, data addresses for accessing the memory 38, various parameters required in executing the memory commands or the file management information in the memory. The register 35 is a function implemented on the register circuit 13 of the memory card 1.

The data buffer 36 is a buffer area for transient storage of data written in the memory 38 or read out from the memory 38. The data buffer 36 is a function implemented on the data buffer circuit 14 of the memory card 1.

The memory I/F controller 37 performs control in executing data readout, data write or data erasure between the data buffer 36 and the memory 38 in accordance with the various information and commands stored in the register 35, or in updating the various information in the register 35. The memory I/F controller 37 is a function implemented by the memory I/F controller 16 on the host device 2.

The memory 38 is a data memory area and is designed as a virtual memory as an intrinsic model through the memory I/F controller 37. The memory 38 is a function implemented by the non-volatile semiconductor memory 17 on the memory card 1.

With the above-described host device and memory card, data stored in other mediums, supervised by the file manager 31, can be transferred to the memory 38 through the parallel interfaces 33, 34. Since the file manager 31 supervises the present memory card and other storage mediums by the operation system (MS-DOS), it is possible to transfer data stored in the memory 38 to the other storage mediums or to transfer data stored in the other storage mediums to the memory 38.

The physical format of the data storage area (non-volatile semiconductor memory 17) of the memory card 1 is now explained.

The memory card 1 is made up by a user area and a system area, in which to store e.g. the inner information of the present memory card 1. Both the user area and the system area can be accessed from the host device 2 using the control commands. It should be noted however that the user area and the system area are formed in respective different address spaces and are accessed by the host device 2 using respective different commands.

The user area is physically split in terms of a block of e.g. 64 Kbytes or 128 Kbytes as a unit. This block represents a unit of batch erasure in the present memory card 1. That is, the erasure block in the flash memory corresponds to the present block.

There are two sorts of the blocks, namely an effective block and a spare block. The effective block is a block where entity data of a file is recorded. The spare block is an area in which substitution data for late defects are recorded The user area is recognized from the host device 2 as being an area which is continuous on the sector basis. However, it is internally managed by logical block numbers, derived from sector numbers, recording valid data, and by physical block numbers. The information showing the relationship of correspondence between the logical block numbers and the physical block numbers is recorded in a redundant area, as a management area for the physical blocks, while being recorded in a system area that cannot be accessed from the host device 2 in a state the relationship of correspondence is arranged as data.

In each block are set physical block numbers specifying the block storage locations. These physical block numbers are set uniquely without dependency on whether a block in question is an effective block or a spare block. In the effective block are recorded the logical block numbers. These logical block numbers are written in predetermined areas in the respective blocks. The logical block numbers are recorded at the time of initializing the present memory card 1. If malfunctions occur in a block, the logical block number of the malfunctioning block is written in the unrecorded spare block by way of substitution of the logical block number. Each block is split in terms of a write/readout unit, termed a page, as a unit. This page is in one-for-one correspondence to the sector in the logical format as later explained.

The logical block number accorded to each block is uniquely associated with the cluster number and the LBA sector number in the logical format as later explained. The data storage area is virtually accessed from the side of the host device 2 with the logical format as later explained. However, the memory I/F controller 16 effects address conversion using a logical/physical conversion table stating the relationship of correspondence between the logical and physical addresses. Thus, the host device 2 is able to access the non-volatile semiconductor memory 17, using the logical address (cluster numbers or LBA sector numbers), without comprehending the location of physical data recording.

The physical format of the system area is hereinafter explained.

In the system area, there is recorded an attribute information area where the information required in controlling the present memory card 1 is recorded.

The data recorded in the attribute information area has the meaning shown in FIG. 6.

In the attribute information area, there are recorded “ATRB info area confirmation”, “Device-information entry”, “System information”, “MBR Values” and “PBR Values”, as shown in FIG. 6.

In the “ATRB info area confirmation”, there are included identification codes for identifying the attribute information area.

The “Device-information entry” indicates each recording position of the following “Device-information (System information, MBR Values, MBR Values and PBR Values)”. The recording positions are represented by offset values of the attribute information area.

In the “System information”, there is recorded the internal information of the present memory card 1. For example, in the “System information”, there are recorded the version, class information, number of bytes in one block, number of sectors in one block, total number of blocks, date and time of assembling, serial numbers, assembly maker numbers, flash memory maker numbers, flash memory model numbers, controller numbers, controller functions, start sector numbers of the block boundaries and device types (read/write feasibility, read-only etc.).

Meanwhile, the ‘number of sectors contained in one block’ and ‘start sector number of the block boundaries’ recorded: in the “System information”, are referenced when the host device 2 records data with the ‘real-time recording mode’. The processing for the ‘real-time recording mode’ will be explained in detail subsequently.

In the “MBR Values”, there are recorded recommended parameters of ‘MBR’ (‘Master Boot Record’) prescribed on the MS-DOS. For example, in the “MBR Values”, there are recorded boot identification, start header number, start cylinder number, system identification, ultimate header number, ultimate sector number, ultimate cylinder number, start LBA sector number and the partition size to be recorded in the MBR. The sector indicated in the start LBA sector number becomes the recording position for the ‘PBR (Partition Boot Record)’, that is, the start position of each partition prescribed on the MS-DOS. It is noted that, although plural partitions may be formed in one storage medium in the MS-DOS, it is assumed in the present embodiment that only one partition is formed in the non-volatile semiconductor memory 17.

The present invention is not limited to application to a memory card having formed only a sole partition, but may be applied to a memory card having formed plural partitions.

In the “PBR Values”, there are recorded recommended parameters of ‘PBR’ prescribed on the MS-DOS. For example, there are recorded in the “PBR Values” the jump codes recorded in the PBR, names of OEM, versions, number of bytes per sector, number of sectors per cluster, number of reserved sectors, number of FATs (number of file allocation tables), number of root directory entries, number of sectors in a medium, medium IDs, number of sectors per head, number of heads, number of hidden sectors, total number of logical sectors, physical drive numbers, expansion boot identification, volume serial numbers, volume head or file system types.

The above is the synopsis of the structure of the physical format of the data storage area of the memory card 1 according to the present invention (non-volatile semiconductor memory 17).

Meanwhile, in the memory card 1 according to the present invention, a command for reading out the attribute information (READ_ATRB) is set as a control command. The host device 2 reads out the “MBR Values” and the “PBR Values” using the READ_ATRB command to render it possible to initialize the memory card 1 with the logical format recommended by the assembly maker. Moreover, in the present memory card 1, there is set a command (FORMAT) for initializing the non-volatile semiconductor memory 17, as a control command. If the host device 2 issues the FORMAT command to the memory card 1, the memory I/F controller 16 refers to the “MBR Values” and the “PBR Values” recorded in the attribute information area in order to initialize the non-volatile semiconductor memory 17 in accordance with the contents of the “MBR Values” and the “PBR Values”. The initialization of the memory card 1 will be explained in detail subsequently.

The logical format applied to the memory card 1 of the present invention is hereinafter explained.

The memory card 1 of the present invention uses the MS-DOS convertible format, as the logical format for the data storage area The MS-DOS convertible format is a file system for supervising the data files recorded in a medium by a hierarchical directory structure. In the MS-DOS convertible format, access to data on the medium is made in terms of what is called a cylinder, a head and a sector as a unit. The actual data readout/write unit to the medium is the sector. The MS-DOS convertible format provides a unit, called a cluster, for supervising the recorded data. The cluster size is a multiple of the sector size. For example, 64 sectors make up a cluster. From the operating system on the side of the host device 2, file management is made on the cluster basis.

In the logical format applied to the memory card 1 of the present invention, the cluster size is smaller than the block size and moreover n times the cluster size, where n is an integer not less than two, becomes the size of one block. For example, when the one-block data size is 128 Kbytes, the data size for one cluster is 32 Kbytes, that is, four clusters are recorded in one block.

The logical format applied to the memory card 1 of the present invention is set so that the boundary position of a block necessarily coincides with the boundary position of the cluster. That is, the setting is such that one cluster is not astride two blocks.

For setting the logical format to the conditions described above, it is sufficient to adjust the recording positions of the file management data of the MS-DOS, such as MBR, PBR, FAT or route directories, or parameters recorded in the respective file management data. The parameters for implementing the logical format under the above conditions are recorded in the “MBR Values” and in the “PBR Values” in the attribute information.

The contents of the file management data of the MS-DOS file are as follows:

The MBR is recorded at the leading end of a user area. The contents stated in the MBR are the same as those stated in the “MBR Values” in the attribute information.

The PBR is stated in a leading sector of each partition. The sector where the PBR is recorded is stated in the start LBA sector number in the MBR. Meanwhile, the LBA sector number is the number uniquely accorded to the respective sectors in the effective blocks or in the substitution blocks for the effective blocks. The LBA sector numbers are accorded in the rising order beginning from the leading sector of the block having the logical block number of 0.

The FAT is recorded over plural sectors beginning from a sector next following the PBR. The FAT represents the connecting state of files, handled in the user area, in terms of clusters as units.

The data recorded on the medium are managed in terms of clusters as units. If the main body of a file is astride plural files, it is necessary to read out a cluster to its end and subsequently to read out the next cluster. However, the next cluster is not necessarily recorded in the physically consecutive positions. Thus, in accessing data recorded on a medium, the host device 2 is in need of the information indicating which is the cluster next following a given cluster. It is in the FAT that this sort of the information is recorded.

The FAT is provided with as many storage areas as there are the clusters on the medium. The cluster numbers, beginning from 02_(hex), are accorded to the totality of the clusters present on the medium. To the respective storage areas in the FAT, there are uniquely accorded the cluster numbers. In each of these storage areas, there is stored the number of the cluster next following the cluster to which the storage area is allocated. Thus, if desired to find out the next cluster connected to a given cluster, it is sufficient to refer to the number stored in the storage area associated with the cluster in question.

Meanwhile, the present memory card 1 records two FATs (FAT1, FAT2) for backup. The physical data size of a given FAT is necessarily constant, even if the data contents are updated, because the number of clusters in the medium is unchanged.

In a route directory entry, there is recorded the entry information of each file and each sub-directory arranged in a root directory The route directory entry is recorded as from the sector next following the last sector in which has been recorded the FAT. The number of bytes in a given entry information is of a prescribed value, while the number of the entries arranged in the route directory is also of a prescribed value. Consequently, the data size of the route directory entry is necessarily constant. Meanwhile, in the FAT32 file system, as an extension of the MS-DOS compatible for, the route directory entry is not handled separately and is placed under cluster management.

In the MS-DOS convertible format, the first cluster (cluster number “02”) is initiated as from the sector next following the above-described file management data. That is, the sectors as from the last sector in which has been recorded the route directory entry becomes an area where the actual files generated by the user are recorded. Thus, the above file management data are recorded in the present memory card 1 so that the first sector of the cluster number 02 necessarily becomes the leading sector of the block. In the present memory card 1, the LBA sector number of the leading sector of a given block in the user area is stated in the ‘start sector number of the block boundary’ in the attribute information.

Meanwhile, the format termed a so-called super-floppy system may be applied to the memory card 1 of the present invention. In the super-floppy system, no management data corresponding to the aforementioned MBR is provided and the PBR is recorded at the leading end of the user area. The present invention may be applied to a format where there is no MBR such as that of the super-floppy system, in addition to the MS-DOS convertible format.

The processing for initializing the memory card 1 by the host device 2 and the data recording method are hereinafter explained.

For enabling the memory card 1 of the present invention to be referenced from the operation system of the host device 2, the memory card 1 needs to be initialized by the filing system of the MS-DOS. For initializing processing, it is sufficient to record at least the file management system (MBR, PBR, FAT or route directory entry). This initializing processing, routinely performed at the time of shipment of the memory card 1, may also be performed by the user as necessary.

There are two methods for initializing the memory card 1. The first method is to write necessary data in a predetermined sector, using the control command for writing. The second method is using the control command for initialization.

For illustrating the first and second methods, the control command is first explained.

As for the memory card 1, it is determined on the interfacing protocol that an operation controlling command is transferred from the host device 2 to the memory I/F controller 16. The control command is stored in a command register in the register circuit 13 by a command set command in the TPC from the host device 2, in a command register in the register circuit 13. If once the control command is stored in the command register, the memory I/F controller 16 executes the operation control in keeping with the control command.

The control command may be enumerated by a command for reading out data from the non-volatile semiconductor memory 17 to the data buffer circuit 14, a command for writing data from the data buffer circuit 14 to the non-volatile semiconductor memory 17, a command for erasing data on the non-volatile semiconductor memory 17, a formatting command for restoring the present memory card 1 to the state at the time of shipment from the plant, and a sleep command for halting the operation of an oscillator 18 of the memory card 1.

A specified example of the control command is hereinafter explained.

A READ_DATA command is a command for reading out data in succession from specified addresses in the user area of the non-volatile semiconductor memory 17. On receipt of this READ_DATA command, the memory I/F controller 16 references an address stored in an address register in the register circuit 13 to access the address on the non-volatile semiconductor memory 17 to read out the data from this address. The data so read out are temporarily transferred to the data buffer circuit 14. If once the data buffer circuit 14 is full, that is if 512 bytes have been read out, the memory I/F controller 16 issues a transfer request interrupt for the host device 2. When the data in the data buffer circuit 14 is read out by the host device 2, the next following data are transmitted from the non-volatile semiconductor memory 17 to the data buffer circuit 14. The memory I/F controller 16 repeats the aforementioned processing until a number of data corresponding to the number of data stored in a data count register in the register circuit 13 has been read out.

The WRITE_DATA command is a command for recording data stored in the data buffer circuit 14 in succession as from the specified address in the user area of the non-volatile semiconductor memory 17. If the WRITE_DATA command is supplied, the memory I/F controller 16 refers to the address stored in the data address register in the register circuit 13 to access the address on the non-volatile semiconductor memory 17 to write data as from this address. The data written is the data stored in the data buffer circuit 14. When the data buffer circuit 14 is depleted, that is when the 512 byte data have been written, the memory I/F controller 16 issues a transfer request interrupt to the host device 2. When the data has been written in the data buffer circuit 14 by the host device 2, the next following data are written from the data buffer circuit 14 to the non-volatile semiconductor memory 17. The memory I/F controller 16 repeats the above processing until writing a number of data corresponding to the number of data stored in the data count register in the register circuit 13.

The READ_ATRB is a command for reading out the attribute information from the non-volatile semiconductor memory 17. When supplied with this READ_ATRB, the memory I/F controller 16 reads out the attribute information in the non-volatile semiconductor memory 17 to transfer the data so read out to the data buffer circuit 14.

The FORMAT command reads out the attribute information from the non-volatile semiconductor memory 17, while reading out “MBR Values” and “PBR Values” in this attribute information to write MBR, PBR, FAT and the route directory entry in the non-volatile semiconductor memory 17 in accordance with the read-out values.

The above explanation is centered about the control command.

If the memory card 1 is to be initialized by the first method, the host device 2 reads out the “MBR Values” and “PBR Values” in the attribute information, using the READ_ATRB command. The host device 2 refers to the values stated in the “MBR Values” and “PBR Values” to generate MBR, PBR, FAT and the route directory. The host device 2 writes the so generated MBR, PBR, FAT and the route directory entry in predetermined sectors stated in the “MBR Values” and “PBR Values”, using the WRITE_DATA command. By the above processing, the memory card 1 is initialized so that it can be referenced by the host device 2.

Meanwhile, the values of the MBR, PBR, FAT and the route directory entry need not be equal to the “MBR Values” or the “PBR Values” in the attribute information and may be uniquely generated by the host device 2.

If the memory card 1 is initialized by the second method, the host device 2 sends the FORMAT command to the memory I/F controller 16 of the host device 2. When supplied with the FORMAT command, the memory I/F controller 16 reads out the “MBR Values” or the “PBR Values” in the attribute information. Based on the values stated in the so read out “MBR Values” or the “PBR Values”, the memory I/F controller 16 writes the MBR, PBR, FAT and the route directory entry in the predetermined sectors in the non-volatile semiconductor memory 17. By the above processing, the memory card 1 is initialized so that it can be referenced by the host device 2.

With the memory card 1 of the present invention, described above, it is possible to selectively perform the two sorts of the initialization, namely a method in which the host device 2 writes the parameters generated by the host device 2 itself, by way of initialization, using the write command (WRITE_DATA command), and a method in which the host device 2 uses a command for initialization (FORMAT command) and in which the memory card 1 automatically performs the initialization. In initializing the memory card 1, the host device 2 is able to use the command for initialization (FORMAT command), so that it is unnecessary for dedicated parameters or an initializing program conforming to the versions or the standards to be enclosed with the result that the initialization can be achieved extremely readily.

The operation when data is recorded from the host device 2 to the memory card 1 is now explained with reference to FIG. 7.

When the memory card 1 is loaded in the slot of the host device 2, the host device reads out the ‘number of sectors contained in one block’ and the ‘start sector number of the block boundary’ from the “System information” in the attribute information, using the command for reading out the attribute information (READ_ATRB command) (step S11).

The host device 2 then is in a standby state until the recording operation is started by the user (step S12).

When the recording operation is started by the user, the host device 2 checks whether the current recording mode is the real-time recording mode or the usual recording mode (step S13).

In case the recording mode is the usual recording mode, processing transfers to a step S14 and, in case the recording mode is the real-time recording mode, processing transfers to a step S15.

It is noted that the real-time recording mode is such a mode in which data recording operation must follow the recording data generating processing as in case of real-time recording of moving picture signals, or in which recording processing needs high speed recording, as in case of recording large volume data. On the other hand, the usual recording mode is such a recording mode in which high speed recording is not needed, as in case of recording a still image. The mode selection of selecting the real-time recording or the usual recording may be manually set by the user or may also be automatically set in meeting with the data recording by the host device 2.

In a step S14, recording processing is carried out on the cluster basis. That is, the FAT is referenced to retrieve a void area on the cluster basis to record data sequentially in the void area found out.

In a step S15, the FAT is referenced to find out a void area which is continuously void for one block interval. If there is such void area which is continuously void for one block interval, data is recorded in such block in succession. That is, should there be a void cluster, but data has already been recorded in another cluster of the block to which belongs the void cluster, no data is recorded in the void cluster. For example, if one block is made up by four clusters, data is recorded in the void cluster on the four-cluster basis.

The host device 2 usually is unable to recognize a block on the physical format. However, in the present memory card 1, the logical format is formed so that the block boundary position is necessarily the cluster boundary position. Thus, if the number of clusters (or sectors) in one block and the cluster number on the block boundary (or the LBA sector number) are known, the block can be recognized from the logical format. Thus, the host device 2 is able to verify the number of clusters in one block and the position of the leading cluster in the block from the ‘number of sectors contained in one block’ and the ‘start sector number of the block boundary’ referenced in the step S11.

If this real-time recording mode is applied, data can be recorded on the block basis, even for a medium in which the erasure block is larger in size than the cluster size, without employing a special file system. Thus, with the present real-time recording mode, data can be recorded without generating the garbage collection which is necessary for protecting the recorded data, and hence recording can be carried out more speedily than if the data is recorded on the cluster basis as usual.

Meanwhile, in the usual file system, it is possible to confirm the vacant capacity in the medium before or during data recording. When the usual recording mode is selected, the host device 2 simply detects the number of void clusters form the FAT to calculate the void capacity. If conversely the real-time recording mode is selected, simply the number of void clusters is detected from the FAT to calculate the void capacity. If conversely the real-time recording mode has been selected, such a block in which the totality of the clusters are unrecorded is detected from the FAT and the void capacity is calculated from the number of the blocks.

A specified instance of formatting of the memory card 1 is now shown. The formatting instance, now explained, is for the memory card 1 in which the total capacity is 64 Mbytes, the sector size is 512 bytes, the cluster size is 32 Kbytes, a block size is 128 Kbytes and the number of sectors needed for recording one FAT is eight. Thus, each cluster is made up by 64 sectors, with each block being made up by four clusters. Meanwhile, in the present instance, such a case is explained in which FAT 16, used in case the total number of clusters exceeds 4085, as an MS-DOS type, is explained. In the FAT 16, the number of bytes allocated to each cluster in the FAT is 2 bytes (16 bits).

FIG. 8 shows an image of a medium of a first specified example. FIG. 9 shows the values of respective parameters of the first specified instance. FIGS. 10 and 11 show the contents of description of the MBR and the PBR of the first specified instance, respectively.

The LBA sector number is a number uniquely attached to the totality of the effective blocks in the medium, without regard to the partitions or boot areas. As for the LBA sector number, the leading sector number is 0, and is sequentially incremented by 1. The block number is the logical block number accorded to each effective block. As for the block number, the leading block is 0 and is sequentially incremented by 1. Meanwhile, in case of substitution of the effective blocks, the LBA sector number and the block number are accorded to the substituted blocks.

In the first specified instance, the MBR is recorded in the leading sector of the block number 0 (with the LBA sector number of 0). The PBR is recorded in the sector of the LBA sector number 462 of the block number 1. The FAT1 and the FAT2 are recorded in the sectors of the LBA sector numbers 464 to 479 of the block number 1. The route directory entry is recorded in the sectors with the sector numbers of 480 to 511 of the block number 1.

By recording the MBR, PBR, FAT and the route directory entry as described above, the leading sector (leading sector of the cluster 2) where there is recorded the file generated by the user is recorded as from the leading sector of the block 2 (LBA sector number 512). As a result, the logical format is such a one in which tie block boundary position is coincident with the cluster boundary position.

A second specified instance of a specified format of the memory card 1 is now explained.

FIG. 12 shows an image of a medium of the second specified instance. FIG. 13 shows the values of respective parameters of the second specified instance. FIGS. 14 and 15 show the contents of description of the MBR and the PBR of the second specified instance, respectively.

The LBA sector number is a number uniquely attached to each of the effective blocks in the medium, without regard to the partitions or boot areas. As for the LBA sector numbers, the leading sector number is 0, and is sequentially incremented by 1. The block number is the logical block number accorded to the respective effective blocks. As for the block number, the leading block is 0 and is sequentially incremented by 1. Meanwhile, in case of substitution of the effective blocks, the LBA sector number and the block number are accorded to the substituted blocks.

In the second specified instance, the MBR is recorded in the leading sector of the block number 0 (with the LBA sector number of 0). The PBR is recorded in the sector of the LBA sector number of 335 of the block number l. The FAT1 and the FAT2 are recorded in the sectors of the LBA sector numbers 336 to 351 of the block number 1. The route directory entry is recorded in the sectors with the sector numbers of 352 to 383 of the block number 1.

By recording the MBR, PBR, FAT and the route directory entry as described above, the leading sector (leading sector of the cluster 2), where the file generated by the user is recorded, is recorded as from the LBA sector number 384 of the block 1. As a result, the logical format is such a one in which the block boundary position is coincident with the cluster boundary position.

In both the first and second specified instances, the block boundary position is the cluster boundary position and block-based batch recording may be made from the host device 2, that is, recording can be made on the four-cluster basis.

Meanwhile, in the FAT16 format, the leading eight bytes are of a prescribed value of “F8FF FFFF”. The FAT16 format also prescribes the area of each cluster every four bytes as from the ninth byte. The cluster number of the first cluster is “2”. In the present instance, the number of bytes per sector is 512. Thus, in the first sector of the FAT, a cluster area from the cluster number 2 to the cluster number 127 is formed.

In the case of the format of the first specified instance, the block 2 is formed by the cluster numbers of 02, 03, 04 and 05, the block 3 is formed by the cluster numbers of 06, 07, 08 and 09, the block 4 is formed by the cluster numbers of 0a, 0b, 0c and 0d and so forth, so that, subsequently, each one block is formed by four clusters, as shown in FIG. 16. Moreover, in the case of the format of the first specified instance, the leading sector of the FAT ends with the second cluster (cluster 7 f) of the block 33. The second sector of the FAT begins with the third cluster (cluster 80) of the block 33. That is, in the format of the first specified instance, the block boundary represented in the FAT is not coincident with the actual sector position of the FAT.

On the other hand, with the format of the second specified instance, the block 1 is formed by the cluster numbers of 02 and 03, the block 2 is formed by the cluster numbers of 04, 05, 06 and 07, the block 3 is formed by the cluster numbers of 08, 09, 0a and 0b, the block 4 is formed by the cluster numbers of 0c, 0d, 0e and 0f, and so forth, so that, subsequently, each one block is formed by four clusters, as shown in FIG. 17. Moreover, in the case of the format of the second specified instance, the leading sector of the FAT ends with the fourth cluster of the block 32, that is the last cluster in the block (cluster 7 f). The second sector of the FAT begins with the first cluster of the block 33. That is, in the format of the second specified instance, the block boundary position represented in the FAT is coincident with the actual sector position of the FAT.

If the actual sector boundary of the FAT is not coincident with the block boundary, represented by the FAT, and the cluster information of the block lying at the sector boundary is to be read, two sectors must be read. If conversely the actual sector boundary of the FAT is coincident with the block boundary, represented by the FAT, it suffices to read out only one sector, even in case the cluster information of the block lying at the sector boundary is to be read.

Thus, the file management on the side of the host device 2 is easier with the format of the second specified instance than with the format of the first specified instance.

In both the first and second instances, the MBR is recorded in a sole block. That is, the MBR is recorded in a block different than the PBR, FAT or the route directory entry. By recording the MBR in the sole block, it becomes possible to provide for file safety in case of a medium where a batch erasure unit is fixed, as in a flash memory. That is, since the MBR is recorded in the PBR, FAT or root directory entry that is liable to be rewritten or in a block different from real data, it becomes unnecessary to rewrite MBR, thus assuring the file safety.

This recording of the MBR in a block different than the block in which to record the PBR, FAT or the route directory entry may be applied even in a case different from the case of the present memory card 1 in which the block size is larger than the cluster size.

Usually, the MBR, PBR, FAT and the route directory entry are recorded in succession on the sector basis, without regard to the block position, as shown in FIG. 18. That is, the MBR and the PBR are recorded in the sector of sector number 0 and in the sector of sector number 1, respectively.

If conversely the cluster size is smaller than the block size, as when the cluster size is 32 Kbytes and the block size is 16 Kbytes, it is sufficient if the MBR is recorded in the sector of the sector number 0 and the PBR is recorded in the sector of the sector number 47, as shown in FIG. 19.

In the case of a memory card in which the cluster size is equal to the block size, as when the cluster size is 16 Kbytes and the block size is 32 Kbytes, it is sufficient if the MBR is recorded in the sector of the sector number 0 and the PBR is recorded in the sector of the sector number 79, as shown in FIG. 20.

The present invention is not limited to the instances described with reference to the drawings and, as may be apparent to those skilled in the art, various changes, substitutions or equivalents may be envisaged without departing from the scope and the purport of the invention as defined in the appended claims.

Industrial Applicability

The data storage device of the present invention includes a non-volatile semiconductor memory that may be erased batch-wise on the block basis, and a system information storage unit, in which is stored the information specifying the number of sectors in one block and the logical addresses of the sectors of the block boundary positions, so that, even in case such a file system is applied in which the maximum size of the data access unit to the semiconductor memory is smaller than the erasure block size of the semiconductor memory, data can be recorded without producing so-called garbage collection. 

1. A removable data storage device detachably mounted to a host apparatus, comprising a non-volatile semiconductor memory in which data recorded thereon is erased batch-wise in terms of a block of a predetermined data volume as a unit; and a system information storage unit having the inner information of the data storage device recorded therein; wherein a user area, as an area in which data is recorded by a user, is provided in a storage area of said semiconductor memory; file management data corresponding to the logical format supervising the recorded data by setting logical addresses from one sector as a data read/write unit to another and also supervising the relationship of interconnection of the recorded data in terms of a cluster, composed of a predetermined number of physically consecutive sectors, as a unit, is recorded in said user area, said user area being accessed by the host apparatus based on said logical format; and wherein the number of sectors in one block and the information indicating the logical address of the sector of the block boundary position are stored in said system information storage unit.
 2. The data storage device according to claim 1 wherein the block size is n times the cluster size, where n is an integer not less than 2, and wherein the logical format is formed so that the leading sector of each block in the user area is coincident with the leading sector of said cluster.
 3. The data storage device according to claim 2 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to each FAT; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 4. The data storage device according to claim 2 wherein said file management data is made up by a partition boot record (PBR), recorded in a sector of a leading logical address in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to each FAT; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 5. The data storage device according to claim 2 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, and a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; recording being made as from a sector next following the route directory entry.
 6. The data storage device according to claim 4 wherein said logical format is set so that a recording area for the interconnection information for n consecutive clusters recorded in one block is formed in a self-complete form in one sector.
 7. The data storage device according to claim 6 wherein a logical sector for recording the PBR is stored in said system information storage unit.
 8. The data storage device according to claim 1 wherein said system information storage unit is formed on a recording area of said semiconductor memory.
 9. A host device on which is detachably mounted a removable data storage device, said host device comprising a host side interface for accessing said data recording device; wherein said data storage device including a non-volatile semiconductor memory in which data recorded thereon is erased batch-wise in terms of a block of a predetermined data volume as a unit; and a system information storage unit having the inner information of the host device recorded therein; wherein a user area, as an area in which data is recorded by a user, is provided in a storage area of said semiconductor memory; file management data corresponding to the logical format supervising the recorded data by setting a logical address from one sector as a data read/write unit to another and also supervising the relationship of interconnection of the recorded data in terms of a cluster, composed of a predetermined number of physically consecutive sectors, as a unit, is recorded in said user area; wherein the number of sectors in one block and the information indicating the logical address of the sector lying at the block boundary position are stored in said system information storage unit, and wherein said host side interface accesses the data storage device based on said logical format.
 10. The host device according to claim 9 wherein the block size is n times the cluster size, where n is an integer not less than 2, and wherein the logical format is formed so that the leading sector of each block in the user area is coincident with the leading sector of said cluster.
 11. The host device according to claim 10 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to each FAT; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 12. The host device according to claim 10 wherein said file management data is made up by a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following the PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to the FAT; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 13. The host device according to claim 10 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, and a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; recording being made as from a sector next following the route directory entry.
 14. The host device according to claim 12 wherein said logical format is set so that a recording area for the interconnection information for n consecutive clusters recorded in one block is formed in a self-complete form in one sector.
 15. The host device according to claim 14 wherein a logical sector for recording the PBR is stored in said system information storage unit of the data storage apparatus.
 16. The host device according to claim 9 wherein said system information storage unit is formed on a recording area of a semiconductor memory.
 17. A data recording system having a host device and a removable data storage device detachably mounted to the host device, wherein said data storage device includes a non-volatile semiconductor memory in which data recorded thereon is erased batch-wise in terms of a block of a predetermined data volume as a unit, and a system information storage unit having the inner information of the data storage device recorded therein; wherein a user area, as an area in which data is recorded by a user, is provided in a storage area of said semiconductor memory; file management data corresponding to the logical format supervising the recorded data by setting logical addresses from one sector as a data read/write unit to another and also supervising the relationship of interconnection of the recorded data in terms of a cluster, composed of a predetermined number of physically consecutive sectors, as a unit, is recorded in said user area; and wherein the number of sectors in one block and the information indicating the logical address of the sector of the block boundary position are stored in said system information storage unit.
 18. The data recording system according to claim 17 wherein the block size is n times the cluster size, where n is an integer not less than 2 and wherein the logical format is formed so that the leading sector of each block in the user area is coincident with the leading sector of said cluster.
 19. The data recording system according to claim 18 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to each FAT; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 20. The data recording system according to claim 18 wherein said file management data is made up by a partition boot record (PBR), recorded in a sector of a leading logical address of said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following said PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to each FAT; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 21. The data recording system according to claim 18 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, and a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; recording being made as from a sector next following the route directory entry.
 22. The data recording system according to claim 20 wherein said logical format is set so that a recording area for the interconnection information for n consecutive clusters recorded in one block is formed in a self-complete form in one sector.
 23. The data recording system according to claim 22 wherein a logical sector for recording the PBR is stored in said system information storage unit.
 24. The data recording system according to claim 17 wherein said system information storage unit is formed on a recording area of a semiconductor memory.
 25. A data management method for a removable data storage device detachably mounted to a host apparatus, said data storage device comprising a non-volatile semiconductor memory in which data recorded thereon is erased batch-wise in terms of a block of a predetermined data volume as a unit, and a system information storage unit having the inner information of the data storage apparatus recorded therein; wherein a user area, as an area in which data is recorded by a user, is provided in a storage area of said semiconductor memory; file management data corresponding to the logical format supervising the recorded data by setting logical addresses from one sector as a data read/write unit to another and also supervising the relationship of interconnection of the recorded data in terms of a cluster, composed of a predetermined number of physically consecutive sectors, as a unit, is recorded in said user area, said user area being accessed by the host apparatus based on said logical format; and wherein the number of sectors in one block and the information indicating the logical address of the sector of the block boundary position are stored in said system information storage unit.
 26. The data management method according to claim 25 wherein the block size is n times the cluster size, where n is an integer not less than 2, and wherein the logical format is formed so that the leading sector of each block in the user area is coincident with the leading sector of said cluster.
 27. The data management method according to claim 26 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to each FAT; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 28. The data management method according to claim 26 wherein said file management data is made up by a partition boot record (PBR), recorded in a sector of a leading logical address of each partition formed in said user area, a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following said PBR, and a route directory entry recorded across a plurality of sectors beginning from the sector of the next logical address to said FAT; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; said entity data recorded in each partition being recorded as from a sector next following the route directory entry.
 29. The data management method according to claim 26 wherein said file management data is made up by a master boot record (MBR), recorded in a sector of a leading logical address of said user area, a partition boot record (PBR), recorded in a sector of a leading logical addresss of each partition formed in said user area, and a file allocation table (FAT) recorded across a plurality of sectors beginning from the sector of the logical address next following each PBR; said MBR stating the logical address of the sector where the PBR has been recorded; said PBR stating the information pertinent to the partition where said PBR has been recorded; said FAT having formed, in association with the totality of the clusters in the partition, an area for storage of the interconnection information specifying the cluster connected next to a cluster in question; said route directory entry stating the entry information for a file arranged in the uppermost directory and a subdirectory; recording being made as from a sector next following the route directory entry.
 30. The data management method according to claim 28 wherein said logical format is set so that a recording area for the interconnection information for n consecutive clusters recorded in one block is formed in a self-complete form in one sector.
 31. The data management method according to claim 30 wherein a logical sector for recording the PBR is stored in said system information storage unit.
 32. The data management method according to claim 25 wherein said system information storage unit is formed on a recording area of a semiconductor memory. 